Methods, devices, and computer readable storage device for providing alerts

ABSTRACT

In determining whether to provide an alert associated with a mobile element to a mobile communication device, speeds and directions of travel of the mobile element and the mobile communication device are determined. A relative location of the mobile communication device is calculated with respect to the mobile element. Based on the relative location of the mobile communication device with respect to the mobile element, a determination is made whether the alert should be provided.

TECHNICAL FIELD

The present disclosure relates generally to telecommunications, and,more particularly, to providing alerts.

BACKGROUND

Drivers of vehicles are often unaware of approaching emergencies, suchas an emergency vehicle. As they drive, drivers may be listening to loudmusic, talking on a phone or to a passenger, focused on the road ahead,etc. Also, modern vehicles are insulated against outside noise, and inthe future, vehicles will likely be better insulated against outsidenoise. A driver is often unaware of an approaching emergency vehicleuntil the vehicle is very close or is actually trying to pass thedriver's vehicle. The driver's delay in acting to move over to allow theemergency vehicle to pass or a startled reaction of the driver innoticing the emergency vehicle may result in an accident.

In busy noisy cities, in particular, drivers may be unaware ofapproaching emergency vehicles due to the additional concentrationrequired for driving. In these areas, drivers often unintentionallyblock emergency vehicles, leading to delays in the response time of theemergency vehicles.

SUMMARY

It should be appreciated that this Summary is provided to introduce aselection of concepts in a simplified form, the concepts being furtherdescribed below in the Detailed Description. This Summary is notintended to identify key features or essential features of thisdisclosure, nor is it intended to limit the scope of the presentdisclosure.

According to an illustrative embodiment, a method is provided forproviding alerts. First information indicating a location of a mobileelement is received, including changes to the location of the mobileelement over a predetermined time period. Second information indicatinga location of a mobile communication device that is located within apredefined vicinity of the mobile element is also received. The secondinformation includes changes to the location of the mobile communicationdevice over the predetermined time period. A speed and a direction oftravel of the mobile element are determined, and a speed and a directionof travel of the mobile communication device are also determined basedon the received second information. A relative location of the mobilecommunication device is calculated with respect to the mobile elementbased on the received first information, the received secondinformation, the speed and the direction of the travel of the mobileelement, and the speed and the direction of travel of the mobilecommunication device. Based on the relative location of the mobilecommunication device with respect to the mobile element, a determinationis made whether the alert associated with the mobile element should beprovided to the mobile communication device.

According to another embodiment, a device is provided for providingalerts. The device includes a processor and a memory. The memory hasstored thereon instruction which, when executed by the processor causethe processor to perform operations. The operations include receivingfirst information indicating a location of a mobile element andreceiving second information indicating a location of a mobilecommunication device that is located within a predefined vicinity of themobile element. The first information includes changes to the locationof the mobile element over a predetermined time period, and the secondinformation includes changes to the location of the mobile communicationdevice over the predetermined time period. The operations furtherinclude determining a speed and a direction of travel of the mobileelement and determining a speed and a direction of travel of the mobilecommunication device based on the received second information. Theoperations further include calculating a relative location of the mobilecommunication device with respect to the mobile element based on thereceived first information, the received second information, the speedand the direction of the travel of the mobile element, and the speed andthe direction of travel of the mobile communication device, anddetermining, based on the relative location of the mobile communicationdevice with respect to the mobile element, whether the alert associatedwith the mobile element should be provided to the mobile communicationdevice.

According to another embodiment, a non-transitory computer readablestorage device has instructions stored thereon which, when executed byprocessor, cause the processor to perform operations. The operationsinclude receiving first information indicating a location of a mobileelement and receiving second information indicating a location of amobile communication device that is located within a predefined vicinityof the mobile element. The first information includes changes to thelocation of the mobile element over a predetermined time period, and thesecond information includes changes to the location of the mobilecommunication device over the predetermined time period. The operationsfurther include determining a speed and a direction of travel of themobile element and determining a speed and a direction of travel of themobile communication device based on the received second information.The operations further include calculating a relative location of themobile communication device with respect to the mobile element based onthe received first information, the received second information, thespeed and the direction of the travel of the mobile element, and thespeed and the direction of travel of the mobile communication device,and determining, based on the relative location of the mobilecommunication device with respect to the mobile element, whether thealert associated with the mobile element should be provided to themobile communication device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an environment in which alerts may be providedaccording to an illustrative embodiment.

FIG. 1B illustrates, in detail, a cellular network environment in whichillustrative embodiments may be implemented.

FIG. 2 illustrates a mobile communication device for receiving an alertaccording to an illustrative embodiment.

FIG. 3 illustrates a device for providing an alert according to anillustrative embodiment.

FIGS. 4A and 4B illustrate examples of scenarios in which mobilecommunication devices within vehicles may be alerted of the approach ofan emergency vehicle, according to illustrative embodiments.

FIG. 5 illustrates a method for providing an alert according to anillustrative embodiment.

DETAILED DESCRIPTION

Detailed illustrative embodiments are disclosed herein. It must beunderstood that the embodiments described and illustrated are merelyexamples that may be embodied in various and alternative forms, andcombinations thereof. As used herein, the word “illustrative” is usedexpansively to refer to embodiments that serve as examples orillustrations. The figures are not necessarily to scale and somefeatures may be exaggerated or minimized to show details of particularcomponents. Specific structural and functional details disclosed hereinare not to be interpreted as limiting.

According to illustrative embodiments, mobile communication devicesequipped with location-tracking capabilities may be used to dynamicallyalert users of the mobile communication devices of emergency conditions,e.g., approaching emergency vehicles, weather events, etc. Using themobile communication device for providing alerts is particularly usefulfor drivers of vehicles, as the location-tracking capabilities of themobile communication device may be leveraged to provide alerts, withoutrequiring installation of expensive emergency avoidance systems withinthe vehicles. Although the description that follows discusses anemergency vehicle alert use case in detail, the disclosure is notlimited to this case. For example, the disclosure may also be applicableto other emergencies, e.g., weather events, such that warnings can betargeted to users of mobile communication devices who are in the path ofdanger.

According to an illustrative embodiment, users of mobile communicationdevices may be provided with an alert that emergency vehicles areapproaching towards his/her area based not only on the geographicallocation of the mobile communication device but also based on the speedand direction of travel of the mobile communication device, as well asthe location, speed, and direction of travel of the emergency vehicle.Drivers having mobile communication devices with them may be providedwith alerts about approaching emergency vehicles so that they can takeappropriate action and stay clear of the emergency vehicles. Thisachieves two purposes; it keeps users of the mobile communicationdevices safe and allows emergency vehicles to have the right of way.

FIG. 1A illustrates an environment in which a system for providingalerts may be implemented according to illustrative embodiments.Referring to FIG. 1A, a mobile element 105, e.g., an emergency vehicle,is in communication with a smart alert server 150 via a base station103B and a mobile switch 115. According to one embodiment, the mobileelement 105 may be an emergency vehicle. The emergency vehicle mayinclude a network device implemented as a mobile communication device orany other device that has location tracking capabilities (such as aglobal positioning system (GPS), triangulation, etc.). This device maybe referred to as a source device.

Although the source device is understood with reference to FIG. 1A asbeing included within the mobile element 105, it should be appreciatedthat the source device may be outside of the mobile element 105. Forexample, if the mobile element 105 is a moving environmental element,e.g., a storm, the location of the mobile element 105 may be tracked,e.g., by a Doppler radar device or other type of device within a weatherstation not included within the mobile element 105. In this scenario,the source device may be implemented with a device within the weatherstation having location tracking capabilities and transmissioncapabilities.

Referring again to FIG. 1A, mobile communication devices 101A, 101B,101C and 101D are equipped with location-tracking capabilities so thattheir locations may be tracked. The speed and direction of travel of themobile communication devices 101A, 101B, 101C and 101D may also betracked or calculated, as described in more detail below. In FIG. 1A,the mobile communication devices 101A, 101B, 101C and 101D are incommunication with GPS satellites 135A and 135B, respectively, such thattheir locations can be tracked. It should be appreciated that othertypes of location tracking, e.g., triangulation, may be used to trackthe locations of the mobile communication devices 101A, 101B, 101C and101D. The mobile communication devices 101A, 101B, 101C, and 101D may bereferred to as destination devices. These devices may be implementedwith a mobile communication device such as that depicted in FIG. 2.

Referring to FIG. 1A, a source device, which may be included within themobile element 105, is in communication with a GPS satellite 135A forlocation tracking. It should be appreciated that other forms of locationtracking, e.g., triangulation, may be used to track the location of themobile element 105. The speed and direction of travel of the mobileelement 105 may also be tracked or calculated, as described in furtherdetail below.

The mobile communication devices 101A, 101B, 101C and 101D that may betracked may be those of a user traveling in a vehicle or outside avehicle. In the case of a weather event, the mobile communication device101A, 101B, 101C and 101D may be that of a user who is stationary butmay still need to be alerted.

According to one embodiment, in an emergency situation involving anemergency vehicle as the mobile element 105, an operator of theemergency vehicle switches on the emergency lights and sirens. Switchingon of the lights may, in turn, cause a signal to be transmitted to thesource device within the emergency vehicle to initiate tracking of thelocation of the emergency vehicle. According to one embodiment, thelocation of the mobile element 105 is determined by GPS. In the case ofpoor GPS cover, the location of the mobile element 105 may be determinedby network location elements, e.g., triangulation of base stationsserving the area in which the mobile element 105 is location. The devicelocation may follow the E911 network location.

Information indicating the location of the mobile element 105 istransmitted to a mobile switch 115 (which may be implemented as a device114 and/or a device 138 as described in detail below with reference toFIG. 1B). The information indicating the location of the mobile element105 is, in turn, transmitted by the mobile switch 115 to a smart alertserver 150. The smart alert server 150 determines the speed anddirection of travel of the mobile element 105 based on the receivedinformation indicating the location of the mobile element 105, as theinformation changes over time. As an alternative, if the source devicewithin the mobile element 105 is equipped with sufficient trackingcapabilities, the speed and direction of travel of the mobile element105 may be provided to the smart alert server 150. In the case of themobile element 105 being an environmental event, such as a storm, thesource device may be a stand-alone device with location/trackingcapabilities which track the location, speed, and direction of travel ofthe mobile element 105 and transmit this information to the smart alertserver 150 via the mobile switch 115 or via any other suitable radiotransmission.

According to one embodiment, receipt of the location information fromthe source device may serve as an indication to the smart alert server150 that there is an emergency, such that destination devices within avicinity of the mobile element 105 need to be tracked and alerted, asappropriate. Thus, responsive to receiving the location information fromthe source device, the smart alerts server 150 requests the mobileswitch 115 to provide locations of all the destination devices withinthe vicinity of the mobile element 105. In the case of the mobileelement 105 being an emergency vehicle, the destination devices withinthe vicinity of the mobile element 105 are those mobile communicationdevices 101A, 101B, 101C and 101D that are connected to, camped on orregistered to the source base station to which the source device isregistered and neighboring base stations. The neighboring base stationsmay be considered those base stations that serve areas that are within apredefined distance of the area served by the source base station. Thus,the vicinity may be predefined such that, for example, it includes thearea served by the source base station and areas served by neighboringbase stations.

Referring to FIG. 1A, for example, the mobile element 105 is incommunication with a base station 103B, which is considered to be thesource base station. Mobile communication device 101B is also incommunication with the base station 103B and thus is considered to be inthe vicinity of the mobile element 105. Mobile communication device 101Ais in communication with a base station 103A, and the coverage area ofthe base station 103A is not close enough to the area covered by thebase station 103B to be considered a neighboring base station. As shownin FIG. 1A, the base station 103A is not even in communication with themobile switch 115. Thus, mobile communication device 101A is notconsidered to be within the vicinity of the mobile element 105. Mobilecommunication devices 101C and 101D are in communication with the basestations 103C and 103D, respectively. The areas served by the basestations 103C and 103D are close enough to the area served by the basestation 103B to be considered neighboring base stations. Thus, mobilecommunication devices 103C and 103D are considered to be within thevicinity of the mobile element 105. The base stations 103A, 103B, 103Cand 103D may be implemented with base stations, such as the basestations 102 and 132 shown in FIG. 1B.

In the case of the mobile element being an environmental event, such asa storm, the vicinity may be predefined such that it includes apredefined area surrounding a location of the mobile element.

According to an illustrative embodiment, the smart alert server 150calculates the speed and direction of travel of the mobile communicationdevices 101B, 101C, and 101D that are within the vicinity of the mobileelement 105, based on the reported locations of the mobile communicationdevices 101B, 101C, and 101D. As an alternative, as indicated above, forthose mobile communication devices having more advanced trackingcapabilities, the speed and direction of travel of the mobilecommunication devices may be calculated by the mobile communicationdevices and transmitted to the smart alert server 150, along with thelocation information, via the mobile switch 115.

The smart alert server 150 maps the locations of the mobilecommunication devices 101A, 101B, 101C and 101D within the vicinity ofthe mobile element 105 and calculates each mobile communication device's101A, 101B, 101C and 101D location relative to the location of themobile element 105. As the locations of the mobile element 105 changesover time, the smart alert server 150 may continually request the mobileswitch 115 to provide the locations of the mobile communication devices101A, 101B, 101C and 101D within the vicinity of the mobile element 105.The smart alert server 150 calculates the relative locations of themobile communication devices 101A, 101B, 101C and 101D with respect tothe mobile element 105 based on the locations, speed and direction oftravel of the mobile element 105 and the mobile communication devices101A, 101B, 101C and 101D. According to illustrative embodiments, themobile communication devices 101A, 101B, 101C and 101D that are withinthe vicinity of the mobile element 105 may be provided with alerts basedon the relative locations of the mobile communication devices 101A,101B, 101C and 101D with respect to the location of the mobile element105 and based on specified parameters. The parameter settings dictatewhich mobile communication devices 101A, 101B, 101C and 101D within thevicinity of the mobile element 105 should be alerted. Differentparameters may be specified for different scenarios. Based on theparameter settings, a subset of the mobile communication devices 101A,101B, 101C and 101D within the vicinity of the mobile element 105 may bealerted. The parameter settings may be stored in advance in the smartalert server 150 and/or may be provided by the source device.

An example of a parameter setting may be an area within a predefinedproximity to the mobile element 105. For example, in the scenario inwhich the mobile element 105 is an emergency vehicle, a parametersetting may indicate that only those mobile communication devices 101A,101B, 101C and 101D that are within 300 feet of the emergency vehicleshould be alerted.

The predefined proximity is just one example of a parameter. Anotherparameter may include travel time. That is, the smart alert server 150may translate travel time into a location radius based on the relativespeeds of the mobile element 105 and the mobile communication devices101A, 101B, 101C and 101D. Thus, the smart alert server 150 may alsodetermine to alert mobile communication devices 101A, 101B, 101C and101D that are approaching an area that is within the predefinedproximity of the location of the mobile element 105 at a speed that iswithin a predefined range with respect to a speed of the mobile element105 such that the mobile communication devices 101A, 101B, 101C and 101Dare within a particular travel time away from the approaching mobileelement 105. In the case of an emergency vehicle, for example, mobilecommunication devices 101A, 101B, 101C and 101D that are within a threeminute travel time away from the location of the mobile element 105 maybe provided with alerts.

Parameter settings may also be set based on the environment. Forexample, in the case of an emergency vehicle traveling on a dividedhighway, parameter settings may be set to indicate that only mobilecommunication devices 101A, 101B, 101C and 101D travelling in the samedirection as the emergency vehicle should be provided with alerts. Thisis described in more detail with reference to FIGS. 4A and 4B.

Based on the parameter settings for any particular alert, the smartalert server 150 determines which mobile communication devices 101A,101B, 101C and 101D should be alerted, and passes this information backto the mobile switch 115. The mobile switch 115, in turn, provides thealerts to the mobile communication devices 101A, 101B, 101C and 101Dthat the smart alert server 150 determines should be alerted.

Referring again to FIG. 1A, assume that the smart alert server 150determines which mobile communication devices 101A, 101B, 101C and 101Dto alert based on which mobile communication devices 101A, 101B, 101Cand 101D are within a predefined proximity of a location of the mobileelement 105. This predefined proximity is illustrated as an area 125,which may be referred to as an alert zone. Mobile communication devices101B and 101C are located within the alert zone 125. Thus, the smartalert server 150 would determine that mobile communication devices 101Band 101C should be provided with alerts and would send alerts to thesedevices via the mobile switch 115. Though mobile communication device101D is within the vicinity of the mobile element 105, the mobilecommunication device 101D is not located within the alert zone 125.Thus, no alert would be provided to the mobile communication device101D. Mobile communication device 101A is not even in the vicinity ofthe mobile element 105. Thus, not only would an alert not be provided tothe mobile communication device 101A, but the location of the mobilecommunication device 101A would not be tracked by the smart alert server150.

According to an illustrative embodiment, the smart alert server 150 maybe included within the same cellular network as the mobile switch 115,as shown in FIG. 1B. As an alternative, the smart alert server 150 maybe provided as a third party device which is in communication withcellular network including the mobile switch 115 via, e.g., theInternet. In either case, the alerts are provided to the mobilecommunication devices 101A, 101B, 101C and 101D via the cellularnetwork.

The embodiments described herein may be implemented in wireless networksthat use illustrative telecommunications standards, such as GlobalSystem for Mobile communications (GSM) and Universal MobileTelecommunications Systems (UMTS) as illustrated in FIG. 1B. It shouldbe understood, however, that the embodiments may be implemented inwireless networks that use any existing or yet to be developedtelecommunications technology. Some examples of other suitabletelecommunication technologies include, but are not limited to, networksutilizing Time Division Multiple Access (TDMA), Frequency DivisionMultiple Access (FDMA), Wideband Code Division Multiple Access (WCDMA),Orthogonal Frequency Division Multiplexing (OFDM), Long Term Evolution(LTE), and various other 2G, 2.5G, 3G, 4G, and greater generationtechnologies. Examples of suitable data bearers include, but are notlimited to General Packet Radio Service (GPRS), Enhanced Data rates forGlobal Evolution (EDGE), the High-Speed Packet Access (HSDPA) protocolfamily, such as High-Speed Downlink Packet Access (HSDPA), EnhancedUplink (EUL) or otherwise termed High-Speed Uplink Packet Access(HSUPA), Evolved HSPA (HSPA+) and various other current and future databearers.

FIG. 1B illustrates details of a wireless communications network inwhich a system for providing alerts to mobile communication devices maybe implemented according to an illustrative embodiment. The networkshown in FIG. 1B includes two radio access networks (RAN). A first RAN100, illustrated in the upper left hand portion of FIG. 1B, is dedicatedto GSM-based network access. A second RAN 140, illustrated in the upperright hand portion of FIG. 1B, is dedicated to UMTS-based networkaccess. The subject disclosure is not limited to the illustratedembodiments for GSM and UMTS network access. Other access technologiesare contemplated, such as LTE, as described above. The first RAN 100 isdescribed immediately below.

The first RAN 100 includes one or more base transceiver stations (BTS)104 for communicating with mobile communication devices. Although notshown for simplicity of illustration, it will be appreciated that themobile communication devices may include, for example, mobile phones,portable computers with integrated, external, removable network accesscards, etc. The BTS 104 is the terminating node for the radio interfacein the first RAN. The BTS 104 can include one or more transceivers 102and can be responsible for ciphering of the radio interface.

The BTS 104 is in communication with a base station controller (BSC)108. The BSC 108 is configured to allocate radio resources to the mobilecommunication devices in communication with the BTS 104, administerfrequencies, and control handovers between BTS's. Although illustratedas a distinct element, the BSC 108 functions can be incorporated in theBTS 104.

The BTS 104 is also in communication with a Location Measurement Unit(LMU) 106, which is, in turn, in communication with aLocation/Positioning Determination Entity (PDE) 110. The PDE 110calculates the location of mobile communication devices usingmeasurements taken by the mobile communication device and/or the LMU106. The BSC 108 is also in communication with the PDE 110 and a ServingMobile Location Center (SMLC)/Serving Mobile Locationing/PositioningCenter (SMPC) 112. The SMLC/SMPC 112 determines the locations of themobile communication devices based on data from the PDE 110 and datafrom a location-determining system, e.g., GPS system 130. Although thedescription below is directed to a GPS system, it should be appreciatedthat any type of location-determining system may be used. The GPS system130 may include GPS transceivers that are in communication with themobile communication devices for obtaining information indicating thelocations of the mobile communication devices. The SMLC/SMPC 112provides location information back to the BSC 108, and the BSC 108provides the location information to a Mobile Switching Center (MSC)114.

The MSC 114 is configured to function as a mobile telecommunicationsswitch. When the MSC 114 receives a communication from the BSC 108 andrecognizes the communication as an emergency or location-basedcommunication from a mobile communication device, the MSC 114 retrieveslocation information for the mobile communication device from the BSC108.

The MSC 114 is also in communication with location databases, such avisiting location register (VLR) that may be colocated with the MSC 114,and a home location register (HLR) 118. The VLR can be logicallyassociated with the MSC 114 as illustrated or can be a separate networkelement. The VLR is a database configured to store all subscriber datathat is required for call processing and mobility management for mobilesubscribers that are currently located in an area controlled by the VLR.

The HLR 118 is a database configured to provide routing information formobile terminated (MT) calls and various messaging communications. TheHLR 118 is also configured to maintain subscriber data that isdistributed to the relevant VLR through the attach process and mobilitymanagement procedures, such as location area and routing area updates.

For providing location-based services, the HLR 118 is in communicationwith the MSC 114 and the VLR via a Commercial Location-Based Service(LBS)/Gateway Mobile Location Center (GMLC) 116. The Commercial LBS GMLC116 communicates with the HLR 118 to acquire user information. TheCommercial LBS GMLC 116 also communicates with and one or more thirdparty LBS applications 122 via a LBS Gateway 120 to providelocation-based services to mobile communication devices communicatingwith the network, such as navigational services, fleet tracking, etc.

For providing emergency services to the mobile communication devices,the MSC 114 is in communication with an E911 GMLC/MobileLocationing/Positioning Center (MPC) 124 and an E911 Local ExchangeCarrier (LEC)/PSAP 126. The E911 GMLS/MPC 124 and the E911 LEC/PSAP 126communicate with an ALI database (ALI DB) 128 containing informationrepresenting a caller's location. The E911 GMLC/MPC 124 and the E911LEC/PSAP 126 match a number of an inbound call, e.g., an inboundtelephone number or ANI information, to a corresponding location of thecaller stored in the ALI DB 128 and then deliver both the number and thelocation to the appropriate emergency service, e.g., fire, police, andor ambulance, for dispatch.

The second RAN 140, illustrated in the upper right hand portion of FIG.1, is dedicated to UMTS-based network access and is now described.Mobile communication devices, such as mobile phones and portablecomputers, may communicate with the RAN 140 via one or more Node Bs 134.The Node B 134 is the terminating node for the radio interface in thesecond RAN 140. Each Node B 134 can include one or more transceivers 132for transmission and reception of data to and from the mobilecommunication devices across the radio interface. Each Node B 134 isconfigured to apply codes to describe channels in a CDMA-based UMTSnetwork. Generally, the Node B 134 performs similar functions for theUMTS network that the BTS 104 performs for the GSM network.

The Node B 134 is in communication with a radio network controller (RNC)136. The RNC 136 is configured to allocate radio resources to the mobilecommunication devices, administer frequencies, and control handoversbetween Node B's 134. Generally, the RNC 136 performs similar functionsfor the UMTS network as the BSC 108 performs for the GSM network.

As shown in FIG. 1B, the RNC 136 includes an SMLC for determining alocation of the mobile communication device based on data from the GPSsystem 130. As an alternative, the SMLC may be included as a distinctelement. The RNC 136 is in communication with a 3G MSC 138, whichperforms similar functions as the MSC 114. Upon receipt of an emergencyor location-based services call from a mobile communication device, the3G MSC 138 communicates with the RNC 136 to obtain information regardingthe location of the mobile communication device.

The 3G MSC 138 is also in communication with the Commercial LBS GMLC116, the E911 GMLS/MPC 124, and the E911 LEC/PSAP 126, which perform thesame functions for the UMTS network as described above for the GSMnetwork.

According to an illustrative embodiment, the smart alert server 150 isin communication with the MSCs 114 and 138 to receive locationinformation for the mobile element 105 and the mobile communicationdevices 101A, 101B, 101C and 101D being tracked and to provide alerts tothose mobile communication devices 101A, 101B, 101C and 101D which thesmart alert server 150 determines should be alerted. As noted above, thesmart alert server 150 may be part of the cellular network shown in FIG.1B or may be implemented with a third party device in communication withthe cellular network.

FIG. 2 illustrates a schematic block diagram of an illustrative device200 with which the mobile communication devices 101A, 101B, 101C, and101D may be implemented, according to an illustrative embodiment. Itshould be appreciated that, in the case of a mobile element 105 being anemergency vehicle, the source device within the emergency vehicle may beimplemented with a device similar to that shown in FIG. 2.Alternatively, the source device may be implemented with anycommunication device capable of providing location information of amobile element 105. Although no connections are shown between thecomponents illustrated in FIG. 2, those skilled in the art willappreciate that the components can interact with each other via anysuitable connections to carry out device functions.

Referring to FIG. 2, the device 200 may be a multimode handset and caninclude a variety of computer-readable media, including volatile media,non-volatile media, removable media, and non-removable media. The term“computer-readable media” and variants thereof, as used in thespecification and claims, can include storage media. Storage media caninclude volatile and/or non-volatile, removable and/or non-removablemedia, such as, for example, RAM, ROM, EEPROM, flash memory or othermemory technology, CDROM, DVD, or other optical disk storage, magnetictape, magnetic disk storage, or other magnetic storage devices or anyother medium that can be used to store information that can be accessedby the device 200.

The device 200 may include a display 201 for displaying multimedia, suchas, for example, text, images, video, and telephone functions, such asCaller ID data, setup functions, menus, music metadata, messages,wallpaper, graphics, Internet content, device status, preferencesettings, and the like. The display 201 may also provide alerts from thesmart alert server 150 in a visual manner to warn the user of the device200 of an approaching emergency. The alert may be in the form of, forexample, a flashing light or a visual message, e.g., “Emergency vehicleapproaching. Move over”.

The device 200 may include a processor 202 for controlling and/orprocessing data. A memory 204 can interface with the processor 202 forthe storage of data and/or applications 206. The applications 206 mayinclude, for example, SMS messaging software, EMS message software, MMSmessaging software, USSD software, a WAP browser, and the like.

The applications 206 may also include a user interface (UI) application208. The UI application 208 can interact with a client 210 (e.g., anoperating system) to facilitate user interaction with devicefunctionality and data, for example, viewing received messages,answering/initiating calls, entering/deleting data, password entry andsettings, configuring settings, address book manipulation, and the like.Such user interaction may be facilitated via, e.g., a keypad or atouchscreen included in the device 200 or communicating with the devicevia the I/O interface 224. Also, according to an illustrativeembodiment, using the UI 208, a user may indicate how he or she wouldlike to be alerted of an approaching emergency. That is, the user mayindicate that an audible alert is preferable to a visual alert or thatan alert that is both audible and visual is preferable. Alternatively,the smart alert server may dictate in what form alerts should beprovided to the user.

The applications 206 may include other applications 212, such as, forexample, add-ons, plug-ins, email applications, music application, videoapplications, camera applications, location-based service (LSB)applications, power conservation applications, game applications,productivity application, entertainment applications, combinationsthereof, and the like, as well as subsystem and/or components.

The applications 206 can be stored in the memory and/or in firmwarecomponents 214 and can be executed by the processor 202. The firmware214 can also store code for execution during initialization of thedevice 200.

A communications component 216 may interface with the processor 202 tofacilitate wired/wireless communication with external systems including,for example, cellular networks, location systems, VoIP networks, localarea networks (LAN's), wide area networks (WAN's), metropolitan areanetworks (MAN's), personal area networks (PAN's), and other networks,which may be implemented using WIFI, WIMAX, combinations andimprovements thereof, and the like. The communications component 216 canalso include a multimode communication subsystem for providing cellularcommunications via different cellular technologies. For example, a firstcellular transceiver 218 can operate in one mode, for example, GSM, andan Nth transceiver 220 can operate in a different mode, for exampleUMTS. While only two transceivers 218, 220 are illustrated, it should beappreciated that a plurality of transceivers may be included. Thecommunications component 216 may also include a transceiver 222 forother communication technologies, such as, for example, WIFI, WIMAX,BLUETOOTH, infrared, IRDA, NFC, RF, and the like. The communicationscomponents 216 may also facilitate reception from terrestrial radionetworks, digital satellite radio networks; Internet based radio servicenetworks, combinations thereof, and the like. The communicationscomponent 216 can process data from a cellular network, a corporatenetwork, a home broadband network, a WIFI hotspot, and the like via anISP, DSL provider, or broadband provider. The communications component216 can be used to receive alerts from the smart alert server 150 viathe mobile switch 115 and the base station with which the device isregistered.

An input/output (I/O) interface 224 may be provided for input/output ofdata and/or signals. The I/O interface 224 may be a hardwire connection,such as, for example, a USB, mini-USB, audio jack, PS2, IEEE 1394,serial, parallel, Ethernet (RJ48), RJ11, and the like, and can acceptother I/O devices such as, for example, keyboards, keypads, mice,interface tethers, stylus pens, printers, thumb drives, touch screens,multi-touch screens, touch pads, trackballs, joysticks, microphones,remote control devices, monitors, displays and liquid crystal displays(LCDs), combination thereof, and the like. It should be appreciated thatthe I/O interface 224 can be used for communication between the device200 and a network or local device instead of, or in addition to, thecommunications component 216.

Audio capabilities may be provided by an audio I/O component 226 thatmay include a speaker for the output of audio signals and a microphoneto collect audio signals. Alerts from the smart alerts server 150 may beprovided in an audible manner via the speaker. For example, the speakermay provide a tone and/or a message, e.g., “Emergency vehicleapproaching. Move over”. The audible alert may be provided inconjunction with or separately from the visual alert.

Although not illustrated, tactile alerts may also be provided, e.g., thedevice 200 may vibrate to alert a user of the device. Also, the alertmay be provided in a graduated form such that the alert becomes moreevident as the mobile element approaches. For example, the audiblemessage may become louder, the visual alert may become brighter, and/orthe tactile alert may become stronger as an emergency vehicle getscloser to a vehicle including the device 200.

The device 200 can include a slot interface 228 for accommodating asubscriber identity system 230 such as, for example, a subscriberidentity module (SIM) or universal SIM (USIM). The subscriber identitysystem 230 instead can be manufactured into the device 200, therebyobviating the need for a slot interface 228. In some embodiments, thesubscriber identity system 230 can store certain features, usercharacteristics, rules, policies, models, contact information, and thelike. The subscriber identity system 230 can be programmed by amanufacturer, a retailer, a user, a computer, a network operator, andthe like.

The device 200 can further include an image capture and processingsystem 232 (image system). Photos and/or videos can be obtained via anassociated image capture subsystem of the image system 232, for example,a camera. The device 200 may also include a video system 234 forcapturing, processing, recording, modifying, and or transmitting videocontent.

A location component 236 may be included to send and/or receive signalssuch as, for example, GPS data, A-GPS data, WIF/WIMAX and or cellularnetwork triangulation data, combinations thereof; and the like. Thelocation component 236 can interface with cellular network nodes,telephone lines, satellites (such as satellites 135A and 135B), locationtransmitters and/or beacons, wireless network transmitters andreceivers, for example, WIFI hotspots, radio transmitters, combinationsthereof and the like. The device 200 may obtain, generate, and/orreceive data to identify its location or can transmit data used by otherdevices, to determine the device location. The location of the device200 can be stored locally in the device 200 and provided to the smartalert server 150 upon request.

The device 200 may also include a power source 238, such as batteriesand/or other power subsystems (AC or DC). The power source 238 caninterface with an illustrative power system or charging equipment via apower I/O component 240.

FIG. 3 is a block diagram of a device 300 with which the smart alertserver 150 may be implemented according to an illustrative embodiment.The device 300 includes a processor 310 that receives information, suchas information indicating the locations of a mobile element 105 and thelocation(s) of mobile communication device(s) 101A, 101B, 101C and 101Dwithin a vicinity of the mobile element 105. In one embodiment, theprocessor 310 may also receive information indicating the speed anddirection of travel of the mobile element 105 and information indicatingthe speed(s) and direction(s) of travel of the mobile communicationdevice(s) 101A, 101B, 101C and 101D within the vicinity of the mobileelement 105. This information is received via I/O Data Ports 320. TheI/O Data Ports 320 can be implemented with, e.g., an interface includingan antenna or other suitable type of transceiver through which data andsignals may be transmitted and received. It should be appreciated thatthe I/O Data Ports 320 can be used for communications between with themobile switch 115.

The processor 310 communicates with a memory 330 via, e.g., anaddress/data bus (not shown). The processor 310 can be any commerciallyavailable or customer processor. The memory 330 is representative of theoverall hierarchy of memory devices containing the software and dataused to implement the functionality of the device 300. The memory 330can include, but is not limited to, the following types of devices:processor registers, processor cache, RAM, ROM, PROM, EPROM, EEPROM,flash memory, SRAMD, DRAM, other volatile memory forms, andnon-volatile, semi-permanent or permanent memory types; for example,tape-based media, optical media, solid state media, hard disks,combinations thereof, and the like.

As shown in FIG. 3, the memory 330 may include several categories ofsoftware and data used in the device 300, including, applications 340, adatabase 350, an operating system (OS) 360, and the input/output (I/O)device drivers 370. As will be appreciated by those skilled in the art,the OS 360 may be any operating system for use with a data processingsystem. The I/O device drivers 370 may include various routines accessedthrough the OS 360 by the applications 340 to communicate with devices,and certain memory components. The applications 340 can be stored in thememory 330 and/or in a firmware (not shown) as executable instructions,and can be executed by the processor 310. The applications 340 includevarious programs that, when executed by the processor 310, implement thevarious features of the device 300, including applications fordetermining the speed(s) and direction(s) of travel of the mobileelement 105 and the mobile communication devices 101A, 101B, 101C and101D within the vicinity of the mobile element 105, applications fordetermining relative location(s) of the mobile element 105 with respectto the mobile communication devices 101A, 101B, 101C and 101D, andapplications for determining what mobile communication devices 101A,101B, 101C and 101D to provide alerts to, based on specified parameters.The applications 340 may be applied to data stored in the database 350,such as the specified parameters, along with data, e.g., received viathe I/O data ports 320, such as the location/speed/direction of travelinformation. The database 350 represents the static and dynamic dataused by the applications 340, the OS 360, the I/O device drivers 370 andother software programs that may reside in the memory 330.

While the memory 330 is illustrated as residing proximate the processor310, it should be understood that at least a portion of the memory 330can be a remotely accessed storage system, for example, a server on acommunication network, a remote hard disk drive, a removable storagemedium, combinations thereof, and the like. Thus, any of the data,applications, and/or software described above can be stored within thememory 330 and/or accessed via network connections to other dataprocessing systems (not shown) that may include a local area network(LAN), a metropolitan area network (MAN), or a wide area network (WAN),for example.

It should be understood that FIG. 3 and the description above areintended to provide a brief, general description of a suitableenvironment in which the various aspects of some embodiments of thepresent disclosure can be implemented. While the description refers tocomputer-readable instructions, embodiments of the present disclosurealso can be implemented in combination with other program modules and/oras a combination of hardware and software in addition to, or in steadof, computer readable instructions. The term “application,” or variantsthereof, is used expansively herein to include routines, programmodules, programs, components, data structures, algorithms, and thelike. Applications can be implemented on various system configurations,including single-processor or multiprocessor systems, minicomputers,mainframe computers, personal computers, hand-held computing devices,microprocessor-based, programmable consumer electronics, combinationsthereof, and the like.

FIGS. 4A and 4B illustrate examples of how alerts may be provided invarious scenarios according to illustrative embodiments. Referring toFIG. 4A, an alert zone 410A may be a predefined area within apredetermined proximity of a moving emergency vehicle 405. As theemergency vehicle 405 moves, so does the predefined alert zone 410A. Inthis scenario, a vehicle 415 is in the path of the emergency vehicle 405and within the alert zone 410A, and a vehicle 420 is approaching thealert zone 410A. Accordingly, mobile communication devices within thevehicles 415 and 420 would be sent alerts by the smart alert server 150.Vehicle 425 is just outside of the alert zone and moving away from thezone 410A. Thus, a mobile communication device within the vehicle 425would not be provided with an alert. Also, the mobile communicationdevice within the vehicle 430, which is not located within the alertzone 410A, and is moving away from the alert zone, would not be providedwith an alert.

FIG. 4B illustrates a scenario in which an emergency vehicle isapproaching vehicles on a divided highway. In this scenario, the alertzone 410B may be predefined such that it does not extend outside of thehighway on which the emergency vehicle is traveling or behind theemergency vehicle but does extend a predetermined distance in thedirection of travel of the emergency vehicle 405. As explained above,the predetermined alert zone is a parameter setting which may be storedin the smart alert server 150 and/or provided by the source device. Itshould be appreciated that the alert zone may be any shape, which may bedetermined, e.g., by the source device or the smart alert server 150,based on the type of emergency and/or the environment.

Referring again to FIG. 4B, vehicle 445 is in the path of the emergencyvehicle 405 and within the alert zone 410B. Thus, the mobilecommunication device in the vehicle 445 would be alerted. Vehicles 450,455, and 460 are not located within the alert zone 410B and would not bealerted.

Although not described above, according to additional embodiments, amobile communication device within an emergency vehicle may be equippedto transmit signal to a traffic light controller to dynamically controltraffic lights on a predefined route to allow the emergency vehicle totravel safely through intersections. The mobile communication device mayalso send a signal to the mobile communication devices which are on apredetermined route of the emergency vehicle (e.g., the route to aspecific hospital) within a certain area to alert those vehicles todetour from the route. The mobile communication device may also causethe mobile communication devices within surrounding vehicles to bealerted as to the proper course of action to take to allow the emergencyvehicle the most expeditious path. For instance, in a divided highwayscenario, the mobile communication devices within the surroundingvehicles may be sent an alert to move to the right by a coordinatedmessage which would allow the left lane to free up and be accessed bythe emergency vehicle.

According to further embodiments, in addition to providing emergencyalerts, the smart alert server 150 may provide information which mayotherwise be relevant to users of mobile communication devices 101A,101B, 101C and 101D within a predefined proximity to a mobile element105, such as a moving point of sale. Such information may includeadvertisements, coupons, etc.

FIG. 5 illustrates a method for providing an alert to a mobilecommunication device according to an illustrative embodiment. Referringto FIG. 5, information indicating a location of a mobile element 105,e.g., an emergency vehicle, is received by the smart alert server 150 atstep 510. This information may be received from a source deviceassociated with the mobile element 105, such as a mobile communicationdevice included within the emergency vehicle. At step 520, informationindicating location(s) of mobile communication device(s) that arelocated within a vicinity of the mobile element 105, e.g., mobilecommunication devices 101B, 101C, and 101D is received by the smartalert server 150. It should be appreciated that the location informationof the mobile element 105 and the mobile communication device(s) 101B,101C and 101D may be received at any time and in any order. For example,the location information of the mobile element 105 and the mobilecommunication devices 101B, 101C and 101D may be continually received bythe smart alert server 150. Alternatively, the location information ofthe mobile element 105 and the mobile communication devices may bereceived upon request by the smart alert server 150. As yet anotheralternative, the location tracking information of the mobile element 105may be provided to the smart alert server 150 by the source device,responsive to the source device detecting that the mobile element 105needs to be tracked, e.g., responsive to an emergency vehicle turning onits sirens and emergency lights. Then, the smart alert server 150 mayrequest the location information of the mobile communication devices101B, 101C and 101D within the vicinity of the mobile element 105. Thesmart alert server 150 may cease to request/receive tracking informationonce there is an indication that the emergency event has ended, e.g.,when the emergency vehicle turns its sirens and lights off.

At step 530, the speed and direction of travel of the mobile element 105are determined by the smart alert server 150. In the case of the mobileelement 105 being an emergency vehicle or some other element including asource device, such as mobile communication device, the smart alertserver 150 may calculate the speed and direction of travel of the mobileelement 105 based on the location of the mobile element 105 over apredetermined time period, e.g., a number of seconds. Alternatively, ifthe source device associated with the mobile element 105 includessufficient tracking capabilities, the speed and direction of travel ofthe mobile element 105 may be calculated by the source device andtransmitted to the smart alert server 150. In the case of a weatherevent, the speed and direction of travel may, alternatively, becalculated by a weather tracker source device and transmittedto/received by the smart alert server 150.

At step 540, the speed and direction of travel of the mobilecommunication device(s) 101B, 101C and 101D are determined, based on thelocation(s) of the mobile communication device(s) 101B, 101C and 101Dover the predetermined time period. The smart alert server 150 maycalculate the speed and direction of travel for the mobile communicationdevice(s) 101B, 101C and 101D based on the location(s) of the mobilecommunication devices 101B, 101C and 101D over a predetermined timeperiod, e.g., a number of seconds. Alternatively, if the mobilecommunication device(s) 101B, 101C and 101D include sufficient trackingcapabilities, the speed and direction of travel of the mobilecommunication device(s) 101B, 101C and 101D may calculated by the mobilecommunication device(s) 101B, 101C and 101D and transmitted to the smartalert server 150. At step 560, the smart alert server 150 calculates arelative location of the mobile communication device(s) 101B, 101C and101D with respect to the mobile element 105 based on the receivedlocation information from the mobile element 105 and the mobilecommunication device(s) 101B, 101C and 101D over the predetermined timeperiod, the speed and direction of travel of the mobile element 105, andthe speed and direction of travel of the mobile communication device(s)101B, 101C and 101D. At step 570, the smart alert server 150 determines,based on the relative location(s) of the mobile communication device(s)101B, 101C and 101D with respect to the mobile element 105 and apredetermined parameter, whether an alert associated with the mobileelement 105 should be provided to the mobile communication device(s)101B, 101C and 101D. The smart alert server 150 may determine, forexample, that the alert should be provided to mobile communicationdevices 101B and 101C which are located within an alert zone 125.

If it is determined that the alert should be provided, the alert isprovided at step 570. If is determined that the alert should not beprovided, the process returns to step 510, and tracking of the locationsof the mobile element 105 and the mobile communication devices continues101B, 101C and 101D.

As indicated in FIG. 5, steps 510 and 520 may be continually repeated,and the relative location(s) may be continually calculated as thelocations, speeds, and/or direction of travel of the mobile element 105and/or the mobile communication devices 101B, 101C and 101D change.Thus, the smart alert server 150 continually receives changes to thelocations(s) of the mobile element 105 and the mobile communicationdevices 101B, 101C and 101D.

It should be understood that the steps or other interactions of theillustrated method are not necessarily presented in any particular orderand that performance of some or all the steps in an alternative order ispossible and is contemplated. The steps have been presented in thedemonstrated order for ease of description and illustration. Steps canbe added, omitted and/or performed simultaneously without departing fromthe scope of the appended claims. It should also be understood that themethod can be ended at any time. In certain embodiments, sonic or allsteps of the method, and/or substantially equivalent steps can beperformed by execution of computer-executable instructions stored orincluded on a non-transitory computer-readable medium.

The law does not require and it is economically prohibitive toillustrate and teach every possible embodiment of the present claims.Hence, the above-described embodiments are merely illustrations ofimplementations set forth for a clear understanding of the claimedsubject matter. Variations, modifications, and combinations may be madeto the above-described embodiments without departing from the scope ofthe claims. All such variations, modifications, and combinations areincluded herein by the scope of this disclosure and the followingclaims.

What is claimed is:
 1. A method comprising: receiving, at a servercomprising a processor, first information indicating a location of amobile element, wherein the first information includes changes to thelocation of the mobile element over a predetermined time period; inresponse to receiving the first information indicating the location ofthe mobile element, requesting, from a mobile switch, second informationindicating a respective location of each mobile communication devicethat is connected to, camped on, or registered to a base station towhich the mobile element is registered; receiving, at the processor, thesecond information indicating the respective location of a mobilecommunication device that is connected to, camped on, or registered tothe base station to which the mobile element is registered, wherein thesecond information includes changes to the respective location of themobile communication device over the predetermined time period, whereinthe mobile switch is remote from the server and the mobile element isdistinct from the mobile communication device; determining, by theprocessor, a speed and a direction of travel of the mobile element;determining, by the processor, a speed and a direction of travel of themobile communication device based on the second information;calculating, by the processor, a relative location of the mobilecommunication device with respect to the mobile element based on thefirst information, the second information, the speed and the directionof the travel of the mobile element, and the speed and the direction oftravel of the mobile communication device; and determining, by theprocessor, based on the relative location of the mobile communicationdevice with respect to the mobile element, whether an alert associatedwith the mobile element should be provided to the mobile communicationdevice.
 2. The method of claim 1, wherein determining the speed and thedirection of travel of the mobile element includes calculating the speedand the direction of travel of the mobile element based on the firstinformation.
 3. The method of claim 1, wherein determining the speed andthe direction of travel of the mobile element includes receivinginformation indicating the speed and the direction of travel of themobile element.
 4. The method of claim 1, wherein determining the speedand the direction of travel of the mobile communication device includescalculating the speed and the direction of travel of the mobilecommunication device based on the second information.
 5. The method ofclaim 1, wherein determining the speed and the direction of travel ofthe mobile communication device includes receiving informationindicating the speed and the direction of travel of the mobilecommunication device.
 6. The method of claim 1, wherein the mobileelement is an emergency vehicle.
 7. The method of claim 1, wherein themobile element is a moving environmental element.
 8. The method of claim1, wherein determining whether the alert should be provided to themobile communication device further comprises determining whether therespective location of the mobile communication device is within apredefined proximity of the location of the mobile element.
 9. Themethod of claim 8, wherein determining whether the alert should beprovided to the mobile communication device further comprisesdetermining whether the speed at which the mobile communication deviceis approaching an area that is within the predefined proximity of thelocation of the mobile element is within a predefined range with respectto the speed of the mobile element.
 10. The method of claim 1, whereindetermining whether to provide the alert to the mobile communicationdevice further comprises determining whether the direction of travel ofthe mobile communication device is within a path of travel of the mobileelement.
 11. The method of claim 1, further comprising, responsive todetermining that the alert should be provided to the mobilecommunication device, initiating transmission of the alert to the mobilecommunication device over a cellular network.
 12. A server comprising: aprocessor; and a memory that stores instructions which, when executed bythe processor, cause the processor to perform operations comprising:receiving first information indicating a location of a mobile element,wherein the first information includes changes to the location of themobile element over a predetermined time period, in response toreceiving the first information indicating the location of the mobileelement, requesting, from a mobile switch, second information indicatinga respective location of each mobile communication device that isconnected to, camped on, or registered to a base station to which themobile element is registered, receiving the second informationindicating the respective location of a mobile communication device thatis connected to, camped on, or registered to the base station to whichthe mobile element is registered, wherein the second informationincludes changes to the respective location of the mobile communicationdevice over the predetermined time period, determining a speed and adirection of travel of the mobile element, determining a speed and adirection of travel of the mobile communication device based on thesecond information, calculating a relative location of the mobilecommunication device with respect to the mobile element based on thefirst information, the second information, the speed and the directionof the travel of the mobile element, and the speed and the direction oftravel of the mobile communication device, and determining, based on therelative location of the mobile communication device with respect to themobile element, whether an alert associated with the mobile elementshould be provided to the mobile communication device.
 13. The server ofclaim 12, wherein determining whether the alert should be provided tothe mobile communication device further comprises determining whetherthe respective location of the mobile communication device is within apredefined proximity of the location of the mobile element.
 14. Theserver of claim 13, wherein determining whether the alert should beprovided to the mobile communication device further comprisesdetermining whether the speed at which the mobile communication deviceis approaching an area that is within the predefined proximity of thelocation of the mobile element is within a predefined range with respectto the speed of the mobile element.
 15. The server of claim 12, whereindetermining whether to provide the alert to the mobile communicationdevice further comprises determining whether the direction of travel ofthe mobile communication device is within a path of travel of the mobileelement.
 16. The server of claim 12, wherein the operations furthercomprise initiating transmission of the alert to the mobilecommunication device over a cellular network.
 17. A non-transitorycomputer-readable storage device storing instructions which, whenexecuted by a processor of a server, cause the processor to performoperations comprising: receiving first information indicating a locationof a mobile element, wherein the first information includes changes tothe location of the mobile element over a predetermined time period; inresponse to receiving the first information indicating the location ofthe mobile element, requesting, from a mobile switch, second informationindicating a respective location of each mobile communication devicethat is connected to, camped on, or registered to a base station towhich the mobile element is registered; receiving the second informationindicating the respective location of a mobile communication device thatis connected to, camped on, or registered to the base station to whichthe mobile element is registered, wherein the second informationincludes changes to the respective location of the mobile communicationdevice over the predetermined time period, wherein the mobile switch isremote from the server and the mobile element is distinct from themobile communication device; determining a speed and a direction oftravel of the mobile element; calculating a speed and a direction oftravel of the mobile communication device based on the secondinformation; calculating a relative location of the mobile communicationdevice with respect to the mobile element based on the firstinformation, the second information, the speed and the direction oftravel of the mobile element, and the speed and the direction of travelof the mobile communication device; and determining, based on therelative location of the mobile communication device with respect to themobile element, whether an alert associated with the mobile elementshould be provided to the mobile communication device.
 18. Thenon-transitory computer-readable storage device of claim 17, whereindetermining whether the alert should be provided to the mobilecommunication device further comprises determining whether therespective location of the mobile communication device is within apredefined proximity of the location of the mobile element.
 19. Thenon-transitory computer-readable storage device of claim 17, whereindetermining whether to provide the alert to the mobile communicationdevice further comprises determining whether the direction of travel ofthe mobile communication device is within a path of travel of the mobileelement.
 20. The non-transitory computer-readable storage device ofclaim 17, wherein the operations further comprise initiatingtransmission of the alert to the mobile communication device over acellular network.